View AN670_5401216.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

rev. 0.2 9/12 copyright ? 2012 by silicon laboratories AN670 AN670 g etting s tarted with the s ilicon l abs p recision 32? a pp b uilder 1. introduction precision32? appbuilder is a software program that ge nerates configuration code fo r mcu devices. the software dynamically generates configuration code for peripheral s, clocks, and pins in user-definable modes, greatly simplifying the device initialization pr ocess. this application note overviews the appbuilder software for the silicon labs 32-bit microcontrollers. figure 1. precision32 appbuilder 2. key points ?? creating and navigating a new project ?? configuring peripherals, clocks, pins, and modes ?? exporting a project 3. relevant documentation precision32 application notes are listed on th e following website: www. silabs.com/32bit-mcu. ?? an663: precision32? mcu family clocking options ?? an664: precision32? cmsis and hal user?s guide ?? an667: getting started with the silicon labs precision32? ide ?? an671: precision32? port i/o crossbar decoder
AN670 2 rev. 0.2 4. creating a new project 1. start a new project by selecting new project? from the file menu, or click the new project? link on the start page. this will display a new project window. figure 2. creating a new project 2. in the new project window, select the family, device, revi sion, and sdk version. each selection will reveal all other possible selections. a. the revision selection is the mcu device revision. b. the sdk version determines the functions used by appbuilder. this selecti on should match the sdk base path. 3. name the project and select the location where the generated source will be exported. 4. select the tool set (ide) and compiler. 5. select the silicon lab s 32-bit sdk base path ( c:\silabs\32bit\si32-x.y by default). this selection should match the sdk version. 6. click ok.
AN670 rev. 0.2 3 5. migrating a project appbuilder includes a project migration feature to update a created project with a new device family, new device within the same family, device revision, or sdk version. th is allows existing and complicated projects to be easily ported without redoing all the peripheral, clock, and pin configurations manually. to migrate a project: 1. go to the project menu and select migrate project... . figure 3. migrating a project 2. in the migrate project dialog, select the new settings. the change family, device, or rev checkbox must be checked to change the hardware platform. if the hardware platform changes, the project should be generated to a new location to prevent any build errors. the show report and create backup options are enabled by default. figure 4. migrate project options this must be checked to change the device type or revision select new sdk version
AN670 4 rev. 0.2 3. press ok . 4. if the show report option remains enabled, appbuilder generate s a report of the migration results. this report contains a summary of the migration process an d any errors, warnings, or messages that resulted from the operation. figure 5. project migration report migration summary
AN670 rev. 0.2 5 6. navigating in appbuilder figure 6 shows the basic appbuilder components: project window, source layout, error and warning list, canvas, toolbox window, power tips, and properties window. figure 6. appbuilder project components 6.1. project window the project window contains the project modes. each mode has a set of peripherals, clock settings, and port i/o configurations. clicking on the part number at th e top of the window will open the projec t properties configured in the new project window and in the properties window. 6.2. source layout the source layout window shows the current files included in the project. each of the files can be opened to view their current state. note: the source files in the source layout window are read-only and do not exist on disk until the project is exported. project window source layout error and warning list properties window toolbox window power tips canvas
AN670 6 rev. 0.2 6.3. error and warning list the error and warning list provides notifications for any configuration errors flagged by appbuilder. double- clicking on an error will automatically open the configuration window that co ntains the error, and the erroneous setting will be highlighted in red. 6.4. properties window the properties window contains the configuration settings fo r the peripheral or module currently selected. 6.5. toolbox window the toolbox window is active when the mode canvas is select ed. this box contains the peripherals available on the device. to add a peripheral to the mode, drag and drop it to the canvas . 6.6. canvas the canvas is the active area of the selected module or mode. 6.7. power tips the power tips window shows helpful information on how to configure the selected module to reduce power consumption.
AN670 rev. 0.2 7 7. adding and configuring peripherals to add a peripheral to a mode: 1. double-click the peripherals canvas from the project window under the desired mode. figure 7. selecting the peripherals canvas 2. click and drag the desired peripheral from the toolbox window into the canvas . 3. the peripheral will now display in the canvas window, and the corresponding peripheral files automatically add to the source layout window. when it is clicked and selected, the properties window displays the configurable properties for that peripheral. select the peripherals canvas drag and drop
AN670 8 rev. 0.2 figure 8. peripheral properties 4. the error and warning list will display any errors in the configur ation. double-clicking on one of the errors in the list will jump to and highlight th e property that needs to be corrected. figure 9. error and warning list select the peripheral peripheral properties peripheral files automatically added
AN670 rev. 0.2 9 8. configuring the device clocks to configure the clocks in a mode: 1. double-click on the clock control canvas in the project window to configure the cl ock control module for the selected mode. figure 10. selecting the clock control canvas 2. each clock source on the left can be sele cted to set the configurable properties in the properties window. figure 11. modifying the clock control canvas 3. the multiplexor selection determines the selected clock source for the system. the clock frequencies shown in the diagram will u pdate automatically based on the selected clock source. 4. each clock destination on the right can be enabled by clicking the checkbox to enable the clock to the module. select the clock control canvas select the clock source this selection determines the clock source.
AN670 10 rev. 0.2 9. configuring the pins there are two types of pins suppor ted by appbuilder: those on a crossbar, and those not on a crossbar. 9.1. crossbar pins to configure the crossbar in a mode: 1. double-click on the corresponding crossbar canvas from the port i/o section in the project window. figure 12. crossbar canvas 2. a peripheral is available to add to the crossbar if it?s placed on the peripherals canvas . 3. click the checkboxes next to the periphera l name to enable the signals on the crossbar. 4. select a pin column to configure the properties for th at pin. multiple pins can be selected and configured at the same time. 5. the pins will update in the pino ut view as they are configured. 6. the pinout and crossbar views can be toggled by using the << and >> arrows in the center of the crossbar canvas . select the crossbar canvas enable peripheral signals peripherals not added to the peripherals canvas are unavailable. pins are updated and displayed here. select a column to configure the pin properties
AN670 rev. 0.2 11 9.2. non-crossbar pins to configure pins not in a crossbar: 1. double-click the non-crossbar pin configuratio n canvas (pb4 on the sim3u167 example device). figure 13. non-crossbar canvas 2. select a pin column to configure the properties for th at pin. multiple pins can be selected and configured at the same time. 3. set the pin properties using the properties window. 4. the pins will update in the pino ut view as they are configured. 5. the non-crossbar pin gr id will expand as pins are as signed to unique functions. select the non-crossbar canvas pins are updated and displayed here. select a column to configure the pin properties
AN670 12 rev. 0.2 9.3. printing the pin diagram once the pinout is complete, right-click on the package area and select print... to print the package drawing with peripheral assignment information. figure 14. printing a pinout right-click on the package area to print
AN670 rev. 0.2 13 10. configuring modes modes consist of sets of peripheral, clock, and pin se ttings. appbuilder can specify multiple modes and the transitions between them. as an example, a system migh t contain a normal operating mode and a low-power operating mode. a new project always starts with a single default mode shown in the project window. 10.1. adding or configuring a mode to add a mode to the project, right-click on a mode already in the project in the project window. this will allow the mode to be cloned into a new mode. alternatively, right-clicking on the project in the project window provides options to create a new mode from any mode in the project or a reset mode , which is a mode with all the peripheral, clock, and pin reset defaults. right-clicking on a mode in the project window also provides two additional options: setting the mode as the default after a reset, and removing the mode from the project. figure 15 shows the menus to add or configure modes. figure 15. adding or configuring a mode to rename a mode, left-click on the mode name in the project window and modify the name in the properties window as shown in figure 16. figure 16. renaming a mode select the mode rename the mode
AN670 14 rev. 0.2 10.2. defining mode transitions mode transitions enable a system to move from one user-defi ned mode to another in an efficient way. mode transition functions include the minimal amount of code to configure the pe ripherals from one mode to the next as opposed to regenerating full initialization code. appbuilder automatically populates some mode transition s. to define a new mode transition, double-click the mode transitions option in the project window. select the mode to transition from and the mode to transition into under add transition . then, click the plus ( + ) button. to remove a transition, click the minus ( ? ) button next to the transition. figure 17. mode transitions transitions from reset will generate peripheral, clock, and pin configuration code. transitions between two user- defined modes will generate peripheral transition code only. ap pbuilder displays a ye llow banner when editing settings for a mode that does not have a transition defined from the reset state as shown in figure 18. to quickly add a transition from reset to the selected mode, click the add the transition link in the banner. figure 18. mode transition warning banner
AN670 rev. 0.2 15 11. estimating power consum ption (sim3l1xx devices only) the appbuilder power estimator can provide real-time es timates of the sim3l1xx device power consumption in each mode. this feature is based on a power model de veloped to estimate power based on dc-dc converter efficiency, ldo output volt age, and enabled peripherals. 11.1. manipulating the power model double-click on the corresponding power estimate for the appropriate mode in the project window to view and modify the power estimate for a mode. figu re 19 shows an example mode power estimate. figure 19. example power estimate the units are shown in power or current using the toggle bu tton at the top. in addition , the view can switch between all available domains or contributing domains. once in the power estimate view, single-click on a power domain in the list or in the pie chart to show its constituent properties in the properties window. select the power estimate for the mode toggle units (power or current) show all domains or only contributing domains total estimate for the mode
AN670 16 rev. 0.2 figure 20. viewing power estimate properties some properties may be disabled if t he peripheral has not been added to the peripheral canvas or if the peripheral?s current configuration does not allow the property to be modified. for a more detailed view of the selected power domain, doub le-click on the power domain to step into a lower level of the power model. click the top-level domain ( vbatdc ) at the top of the window to return to the top-level power estimate. ldo0: vdigital selected
AN670 rev. 0.2 17 figure 21. detailed power domain information
AN670 18 rev. 0.2 11.2. comparing power estimates the status bar at the bottom of the appbuilder window shows the total power consumption for the selected mode as well as the effect (positive or negative) of the last property change on the power estimate. in addition to estimating the power consumption for th e mode?s current configuration, appbuilder can store a previous power estimate to enable quick comparisons of power consumption between groups of property changes. to see the effects of multiple property changes on the power consumption for a mode: 1. show the previous power model estimate by clicking the show previous power shapshot button. 2. press the pause updates button to freeze the pr evious power estimate. 3. make any necessary property changes. figure 22. comparing power estimates as properties and configurations chan ge, the current power estimate will co ntinue updating, while the previous estimate will stay frozen, allowing for in -depth comparison of power domains. the previous power estimate can still be interacted with, but properties displayed in the previous power estimate cannot be modified. show previous power snapshot pause updates power status double-click to view more detail
AN670 rev. 0.2 19 12. viewing source code the generated source code can be viewed at any time durin g the configuration process by double-clicking on a file in the source layout window. the source files in the source layout window are read-only and do not exist on disk until the project is exported. double-click a file in the source layout window. generated files will be in th e generated folder . this source will dynamically change as properties and settings change during configuration. figure 23. generated source code select the guart0 c source file
AN670 20 rev. 0.2 13. generating a project fo r development and debugging when configuration is complete, generate a project by selecting export source... from the file menu or by clicking the export source button in the toolbar. figure 24. exporting a project this will open the export source dialog shown in figure 25. if the workspace or project does not already exis t, appbuilder will create the workspace and all my- and g- files. if the workspace or project already exists, appbuilder will regenerate the g- files but leave all existing my- files alone. appbuilder expects that my- files are edited by the user and does not overwrite them . appbuilder will indicate any potential problems with the selected workspace or project and the export file status in the expanded source tree. selecting the open after export checkbox will cause appbu ilder to launch the selected ide. clicking the ok button will export the project to the location specified in the project properties.
AN670 rev. 0.2 21 figure 25. export project dialog export file status
AN670 22 rev. 0.2 d ocument c hange l ist revision 0.1 to revision 0.2 ?? added descriptions for the project migration and power estimator features. ?? updated "6. navigating in appbuilder" on page 5 and figure 6 to include power tips.
AN670 rev. 0.2 23 n otes :
AN670 24 rev. 0.2 c ontact i nformation silicon laboratories inc. 400 west cesar chavez austin, tx 78701 tel: 1+(512) 416-8500 fax: 1+(512) 416-9669 toll free: 1+(877) 444-3032 please visit the silicon labs technical support web page: https://www.silabs.com/support/pages/contacttechnicalsupport.aspx and register to submit a technical support request. silicon laboratories and silicon labs are trademarks of silicon laboratories inc. other products or brandnames mentioned herein are trademarks or registered trademarks of their respective holders. the information in this document is believed to be accurate in all respects at the time of publication but is subject to change without notice. silicon laboratories assumes no responsibility for errors and omissions, and disclaims responsib ility for any consequences resu lting from the use of information included herein. a dditionally, silicon laboratorie s assumes no responsibility for the functioning of und escribed features or parameters. silicon laboratories reserves the right to make changes without further notice . silicon laboratories makes no wa rranty, rep- resentation or guarantee regarding the suitability of its products for any particular purpose, nor does silicon laboratories as sume any liability arising out of the application or use of any product or circuit, and s pecifically disclaims any an d all liability, including wi thout limitation conse- quential or incidental damages. silicon laborat ories products are not designed, intended, or authorized for use in applications intended to support or sustain life, or for any other application in which the failure of the silicon laboratories product could create a s ituation where per- sonal injury or death may occur. should buyer purchase or us e silicon laboratories products for any such unintended or unauthor ized ap- plication, buyer shall indemnify and hold silicon laboratories harmless against all claims and damages.

▲Up To Search▲

Price & Availability of AN670

	To Download AN670 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .